The Address plus Port (A+P) Approach to the IPv4 Address Shortage
نویسنده
چکیده
We are facing the exhaustion of the IANA IPv4 free IP address pool. Unfortunately, IPv6 is not yet deployed widely enough to fully replace IPv4, and it is unrealistic to expect that this is going to change before the depletion of IPv4 addresses. Letting hosts seamlessly communicate in an IPv4 world without assigning a unique globally routable IPv4 address to each of them is a challenging problem. This document proposes an IPv4 address sharing scheme, treating some of the port number bits as part of an extended IPv4 address (Address plus Port, or A+P). Instead of assigning a single IPv4 address to a single customer device, we propose to extend the address field by using bits from the port number range in the TCP/UDP header as additional endpoint identifiers, thus leaving a reduced range of ports available to applications. This means assigning the same IPv4 address to multiple clients (e.g., Customer Premises Equipment (CPE), mobile phones), each with its assigned port range. In the face of IPv4 address exhaustion, the need for addresses is stronger than the need to be able to address thousands of applications on a single host. If address translation is needed, the end-user should be in control of the translation process-not some smart boxes in the core. Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
منابع مشابه
Comparison Between IPv4 to IPv6 Transition Techniques
The IPv4 addresses exhaustion demands a protocol transition from IPv4 to IPv6. The original transition technique, the dual stack, is not widely deployed yet and it demanded the creation of new transition techniques to extend the transition period. This work makes an experimental comparison of techniques that use dual stack with a limited IPv4 address. This limited address might be a RFC 1918 ad...
متن کاملAn ARP Based Approach for Port Scavenging and IPv4 Address Sharing
The Internet is rapidly nearing IPv4 address space exhaustion. Current projections predict that within the next two years, all IPv4 address blocks will have been assigned. IPv6 adoption on the other hand has not ramped up as rapidly. As we transition from an Internet built on an abundance of IP addresses to one of scarcity, innovative techniques that allow us to do more with less are likely to ...
متن کاملErlang-based dimensioning for IPv4 Address+Port translation
As the IPv4 address pool is being exhausted, it becomes urgent to find a way to migrate IPv4 network architectures to IPv6, or to reduce the use of IPv4 addresses. In this paper, we discuss a strategy known as “Address + Port” translation, which consists in several users sharing the same IPv4 address and being distinguished by a range of port numbers. Of critical importance for the feasibility ...
متن کاملDoing More with Less: End-to-End Consistent IPv4 Address Sharing
The Internet is rapidly nearing IPv4 address space exhaustion. Current projections predict that within the next two years, all IPv4 address blocks will have been assigned. IPv6 adoption on the other hand has been slower than anticipated. It is becoming increasingly clear that there will be an extended period of during which both protocols will coexist as services and applications are slowly mig...
متن کاملNAT Port Mapping Protocol (NAT-PMP)
This document describes a protocol for automating the process of creating Network Address Translation (NAT) port mappings. Included in the protocol is a method for retrieving the external IPv4 address of a NAT gateway, thus allowing a client to make its external IPv4 address and port known to peers that may wish to communicate with it. From 2005 onwards, this protocol was implemented in Apple p...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
- RFC
دوره 6346 شماره
صفحات -
تاریخ انتشار 2011